NOTE: When interworking with a system that does not support the RLT feature, ensure that the associated trunk is not programmed as a Release Link Trunk. Implementing Automatic Route Selection will ensure efficient use of Release Link Trunks.
To activate the MSDN RLT feature:
Trunk
Attributes form
Specify the type of trunk assigned the trunk service number from the RLT field. Use:
"DPN" for DPNSS trunks
"E&M" for E&M trunk
To achieve the maximum usage of DPNSS trunks that connect a particular system to the attendant system:
Configure all DPNSS trunks as RLTs.
From this group of DPNSS trunks, create two overlapping groups of trunks as shown in the following table:
RLT |
GROUP 1 |
GROUP 2 |
1 |
x |
|
2 |
x |
|
3 |
x |
|
4 |
x |
|
5 |
x |
|
6 |
x |
|
7 |
x |
x |
8 |
x |
x |
9 |
x |
x |
10 |
x |
x |
11 |
x |
x |
12 |
x |
x |
Program GROUP 1 to include all the RLTs available.
Program GROUP 2 to include a subset of the available RLTs (7 to 12)
NOTE: In the scheme outlined in the above table, RLT 1 to RLT 6 are dedicated to only attendant-seeking calls. However, if an attendant-seeking call encounters busy from one of those RLTs and an RLT between 7 and 12 is not busy, then the call can use the available RLT to reach the attendant. The reverse is not true for non-attendant-seeking calls. If a non-attendant-seeking call encounters busy from an RLT between 7 and 12, then the call can not use an available RLT between 1 and 6.